-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
handle git cli errors as pkgerrors #3538
handle git cli errors as pkgerrors #3538
Conversation
Co-Authored-By: Fredrik Ekre <11698744+fredrikekre@users.noreply.github.com>
5623a65
to
ae84218
Compare
Any idea why this broke windows? Seems like it's waiting on input or something now |
Revert "debug - run CI with logs on" This reverts commit a8f8125. Update test.yml
.github/workflows/test.yml
Outdated
@@ -61,7 +61,7 @@ jobs: | |||
- run: julia --project --color=yes --check-bounds=yes -e 'import Pkg; Pkg.build(); Pkg.test(; coverage=true)' | |||
env: | |||
JULIA_PKG_SERVER: ${{ matrix.pkg-server }} | |||
JULIA_PKG_TEST_QUIET: "true" # "true" is the default. i.e. tests are quiet when this env var isn't set | |||
JULIA_PKG_TEST_QUIET: "false" # "true" is the default. i.e. tests are quiet when this env var isn't set |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be reverted for the merge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. Converted to draft
It seems like the git cli on the Windows CI machines is interactively requesting creds or something from the user for a simple Anyone know how to fix it? |
Ok. I've just avoided extending the tests to Windows, with TODOs |
(cherry picked from commit b612bfd)
(cherry picked from commit b612bfd)
(cherry picked from commit b612bfd)
Without this if you're offline and using the git cli
With this PR
The
is a little untidy but I thought it best to not capture stderr in case the git cli is asking the user for user credentials etc.